Avoiding multiple retransmissions of signalling transported by 5g nas transport

ABSTRACT

Embodiments herein relate to a wireless device and an Access and Mobility Management Function, AMF, and methods performed by a wireless device and an AMF, respectively.

INTRODUCTION

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

3GPP TR 24.890 v1.0.3 (2017-09) “3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals; 5GSystem—Phase 1; CT WG1 Aspects (Release 15) (“3GPP TR 24.890”) is herebyincorporated by reference, and specifically clause 8.5.1 5GMM commonprocedures, and clause 9.4 5GS session management procedures.

There currently exist certain challenge(s). The current version of 3GPPTR 24.890 defines transport of 5GSM (5G session management) messagesfrom a UE to a SMF via a AMF and back from the SMF to the UE via theAMF.

As explained in the current version of 3GPP TR 24.890, in order totransmit a 5GSM message, the UE sends an uplink (UL) session management(SM) MESSAGE TRANSPORT message comprising the 5GSM message, PDU sessionID and other parameters (e.g. DNN) to an access mobility function (AMF).

Upon receiving the UL SM MESSAGE TRANSPORT message comprising the 5GSMmessage, PDU session ID, and other parameters from the UE, the AMFselects an SMF (if not selected already for the PDU session), based onthe received UL SM MESSAGE TRANSPORT message, and forwards the 5GSMmessage to the selected SMF.

In some embodiments, the AMF may not be able to select a SMF for thereceived UL SM MESSAGE TRANSPORT message. For example, a data networkname (DNN) provided by the UE along with the 5GSM message in the UL SMMESSAGE TRANSPORT message may not be authorized for the UE.

The current version of 3GPP TR 24.890 does not specify how the AMFinforms the UE about a failure to select a SMF for the received UL SMMESSAGE TRANSPORT message.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges.

In some embodiments, if the AMF cannot select a SMF based on a receivedtransport message (e.g., UL SM MESSAGE TRANSPORT message) comprising aSM message (e.g., 5GSM message), the AMF may create a status message(e.g., 5GMM STATUS message) comprising the received transport messageand an indication of a cause of failure to select a SMF for the SMmessage.

In some embodiments, the UE may receive the status message (e.g., 5GMMSTATUS message) transmitted by the AMF. In some embodiments, the statusmessage may comprise the transport message (e.g., UL SM MESSAGETRANSPORT message). Based on the received status message, the UE mayretrieve the SM message (e.g., 5GSM message) included in the transportmessage and unsuccessfully complete the session management transaction(e.g., 5GSM transaction) identified by a procedure transaction identity(PTI) information element (IE) included in the SM message.

There are, proposed herein, various embodiments which address one ormore of the issues disclosed herein.

In some embodiments, a method implemented in a wireless device isprovided. The method includes transmitting a transport message (e.g., ULSM Message Transport message) to an Access and Mobility Function (AMF),wherein the transport message comprises a SM message (e.g., 5GSMmessage); and receiving a status message (e.g., 5GMM Status message)transmitted by the AMF, wherein the status message comprises at least aportion of the transport message and an indication of non-delivery ofthe SM message. In some embodiments the indication of non-delivery is anindication of non-delivery to a SMF.

In some embodiments, a method implemented in an Access MobilityManagement Function (AMF) is provided. The method includes receiving atransport message (e.g., UL SM Message Transport message) transmitted bya wireless device, wherein the transport message comprises a SM message(e.g., 5GSM message); determining whether the SM message can beforwarded to a SMF; as a result of determining that the SM messagecannot be forwarded to a SMF, creating a status message (e.g., 5GMMStatus message) comprising at least a portion of the transport messageand an indication of non-delivery of the SM message to a SMF; andtransmitting the status message to the wireless device. In someembodiments, the determining whether the SM message can be forwarded toa SMF is at least partly based on the transport message.

Certain embodiments may provide one or more of the following technicaladvantage(s).

The current disclosure allows the AMF to notify the UE regarding afailure by the AMF to forward 5GSM messages transmitted by the UEtowards a SMF.

ADDITIONAL EXPLANATION

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art. Additional information may also be found inthe document(s) provided in the Appendix.

As explained in the current version of 3GPP TR 24.890, in order totransmit a 5GSM message, the UE sends a transport message (e.g., uplink(UL) session management (SM) MESSAGE TRANSPORT message) comprising asession management (SM) message (e.g., 5GSM message), PDU session ID andother parameters (e.g. DNN) to an access mobility function (AMF).

Upon receiving the transport message comprising the SM message, PDUsession ID, and other parameters from the UE, the AMF selects an SMF (ifnot selected already for the PDU session), based on the receivedtransport message, and forwards the SM message to the selected SMF.

Clause 8.5.1.1.2.1.1.4 of 3GPP TR 24.890 explains abnormal cases on thenetwork side regarding UE-initiated SM message transport procedureswhere the AMF may be unable to select a SMF based on the transportmessage.

In some embodiments, a first abnormal case may be where the AMF does nothave a PDU session routing context for the PDU session ID of thetransport message and the UE, the request type IE of the transportmessage is set to “initial request,” and the AMF fails to select a SMF.

In some embodiments, a second abnormal case may be where the AMF doesnot have a PDU session routing context for the PDU session ID of thetransport message and the UE, the request type IE of the transportmessage is set to “existing PDU session,” and the user's subscriptioncontext obtained from a unified data management (UDM) does not containan SMF ID corresponding to: (i) the DNN of the transport message, if theDNN is included in the transport message; or (ii) a default DNN, if theDNN is not included in the transport message. In these scenarios, theAMF may fail to select a SMF.

In some embodiments, another abnormal case may be where the UE does notprovide a request type in the transport message. The AMF may be unableto select a SMF based on the transport message.

The current version of 3GPP TR 24.890 does not specify how the AMFinforms the UE about the failure to select a SMF, as described, forinstance, in the abnormal cases described above. Accordingly, theabsence of any specification of such may result in determining that thefailure is due to a permanent cause (e.g. the requested DNN is notauthorized DNN for the UE) and the UE may retransmit the SM message in anew transport message to the AMF. Upon receipt of the new transportmessage, the AMF may need to repeat the same SMF selection only toresult in the same failure to select a SMF.

In some embodiments, the SM transport procedures (clause 8.5.1.1.2.1) asdescribed by 3GPP TR 24.890 may be improved as described in the presentdisclosure below.

In some embodiments, if the AMF is unable to forward the SM message(e.g., 5GSM message) of the transport message (e.g., UL SM MESSAGETRANSPORT message), the AMF may create and send a status message (e.g.,5GMM STATUS message) to the UE. The status message may comprise a 5GMMmessage container IE containing the transport message, and a cause offailure to forward the SM message.

In some embodiments, if the UE receives the status message comprisingthe 5GMM message container IE containing the transport messagecontaining the SM message, the 5GMM layer may inform the 5GSM layerabout non-delivery of the SM message. Based on the notification aboutthe non-delivery of the SM message, the 5GSM procedure may stop anyretransmissions of the SM message and consider the 5GSM procedure asunsuccessfully completed.

In some embodiments, the AMF may create the status message based on afailure of the AMF to select a SMF as described above, for instance, inthe first abnormal case. For example, the AMF may create the statusmessage if the AMF does not have a PDU session routing context for thePDU session ID of the transport message and the UE, the request type IEof the transport message is set to “initial request,” and the AMF failsto select a SMF. The AMF may set a 5GMM message container IE of thecreated status message to the U transport message, according to someembodiments. The AMF may set a cause IE of the created status message toa cause indicating a cause of failure to select a SMF. The AMF may sendthe created status message to the UE.

In some embodiments, the AMF may create the status message based on afailure of the AMF to select a SMF as described above, for instance, inthe second abnormal case. For example, the AMF may create the statusmessage if the AMF does not have a PDU session routing context for thePDU session ID of the transport message and the UE, the request type IEof the transport message is set to “existing PDU session,” and theuser's subscription context obtained from a unified data management(UDM) does not contain an SMF ID corresponding to the DNN of thetransport message, if the DNN is included in the transport message. TheAMF may set a 5GMM message container IE of the created status message tothe transport message, according to some embodiments. The AMF may set acause IE of the created status message to a cause indicating a cause offailure to select a SMF. The AMF may send the created status message tothe UE.

As another example, the AMF may create the status message if the AMFdoes not have a PDU session routing context for the PDU session ID ofthe transport message and the UE, the request type IE of the transportmessage is set to “existing PDU session,” and the user's subscriptioncontext obtained from a unified data management (UDM) does not containan SMF ID corresponding to a default DNN, if the DNN is not included inthe transport message. The AMF may set a 5GMM message container IE ofthe created status message to the transport message, according to someembodiments. The AMF may set a cause IE of the created status message toa cause indicating a cause of failure to select a SMF. The AMF may sendthe created status message to the UE.

In some embodiments, the AMF may create the status message based on afailure of the AMF to select a SMF when the AMF does not have a PDUsession routing context for the PDU session ID of the transport messageand the UE, and the request type IE of the transport message is notprovided. The AMF may set a 5GMM message container IE of the createdstatus message to the transport message, according to some embodiments.The AMF may set a cause IE of the created status message to a causeindicating a cause of failure to select a SMF. The AMF may send thecreated status message to the UE.

In some embodiments, clause 8.5.1.1.2.1.1 of 3GPP TR 24.890 may beimproved to describe embodiments where a UE-initiated SM messagetransport initiation is not accepted by the network.

The UE may receive the status message (e.g., 5GMM STATUS message)transmitted by the AMF described above, according to some embodiments.Upon reception of the status message with the 5GMM message container IEcontaining the transport message (e.g., UL SM MESSAGE TRANSPORTmessage), the UE may pass a non-delivery indication along with the SMmessage (e.g., 5GSM message) of the transport message to the 5GSMprocedures specified in clause 9 of 3GPP TR 24.890. Specifically, themobility management layer of the UE may pass the non-delivery indicationalong with the SM message to the session management protocol layer ofthe UE to notify that the SM message could not be forwarded by the AMF.

In some embodiments, the 5GS session management procedures (clause 9.4)as described by 3GPP TR 24.890 may be improved as described in thepresent disclosure below.

Clause 9.4.2.5 of 3GPP TR 24.890 describes abnormal cases in the UE inUE-requested PDU session establishment procedures. In some embodiments,the session management protocol layer of the UE may receive anon-delivery indication from the mobility management layer of the UEalong with a session establishment request message (e.g., PDU SESSIONESTABLISHMENT REQUEST message) with PTI IE set to the allocated PTIvalue. In some embodiments, the non-delivery indication may be a UEinternal indication triggered by the UE receiving the status message(e.g., 5GMM STATUS message) transmitted by the AMF. Upon receipt of thenon-delivery indication along with the session establishment requestmessage with the PTI IE set to the allocated PTI value, the UE may stopa timer (e.g, Tx), release the allocated PTI value and consider that thePDU session is not established.

Clause 9.4.4.5 of 3GPP TR 24.890 describes abnormal cases in the UE inUE-requested PDU session modification procedures. In some embodiments,the session management protocol layer of the UE may receive anon-delivery indication from the mobility management layer of the UEalong with a session modification request message (e.g., PDU SESSIONMODIFICATION REQUEST message) with a PTI IE set to the allocated PTIvalue. In some embodiments, the non-delivery indication may be a UEinternal indication triggered by the UE receiving the status message(e.g., 5GMM STATUS message) transmitted by the AMF. Upon receipt of thenon-delivery indication along with the session modification requestmessage with the PTI IE set to the allocated PTI value, the UE may stopa timer (e.g., Tk), release the allocated PTI value and consider thatthe PDU session is not modified.

Clause 9.4.6.5 of 3GPP TR 24.890 describes abnormal cases in the UE inUE-requested PDU session release procedures. In some embodiments, thesession management protocol layer of the UE may receive a non-deliveryindication along with a session release request message (e.g., PDUSESSION RELEASE REQUEST message) with a PTI IE set to the allocated PTIvalue. In some embodiments, the non-delivery indication may be a UEinternal indication triggered by the UE receiving the status message(e.g., 5GMM STATUS message) transmitted by the AMF. Upon receipt of thenon-delivery indication along with the session release request messagewith the PTI IE set to the allocated PTI value, the UE may stop a timer(e.g., Tz), release the allocated PTI value and consider that the PDUsession is not released.

In some embodiments, alternative improvements to 3GPP TR 24.890 may beprovided as described by the present disclosure below.

Alternative (1): the UE-initiated NAS transport procedure may beextended with a transport accept message (e.g., UL SM MESSAGE TRANSPORTACCEPT message) or a transport reject message (e.g., UL SM MESSAGETRANSPORT REJECT message), which AMF sends upon reception and handlingof a transport request message (e.g., UL SM MESSAGE TRANSPORT REQUESTmessage), according to some embodiments. Only up to one UE-initiated NAStransport procedure may be run at any given time. If the AMF is able toforward a SM message (e.g., 5GSM message) of the transport requestmessage, the AMF may send the transport accept message. If the AMF isunable to forward the SM message of the transport request message, theAMF may send the transport reject message. In some embodiments, thetransport request message may contain a cause of failure to forward theSM message of the transport request message cause. Accordingly,reliability may be provided on SM transport layer, and the 5GSMprocedure will not need to retransmit the SM message. If transport ofthe SM message fails, the UE will receive the transport reject messageand the 5GSM procedure will consider the 5GSM procedure asunsuccessfully completed.

In some embodiments, alternative (1) may require two NAS messages totransport the SM message while the existing procedure described in 3GPPTR 24.890 requires one NAS message.

Alternative (2): the AMF may be configured with a default SMF forrejection, according to some embodiments. The AMF may route any SMmessage (e.g., 5GSM message) which the AMF is unable to route forward tothe default SMF for rejection. Accordingly, the default SMF may rejectthe SM message with an appropriate response message (e.g., 5GSM responsemessage).

In some embodiments, alternative (2) requires deployment of an SMF. Insome embodiments, the SMF may not have to be fully functional. Forexample, the SMF may only need to be able to reject the SM message fromthe UE.

Alternative (3): the AMF may do nothing and continue to receiveretransmissions of the SM message (e.g., 5GSM message) from the UE whenthe AMF is not able to select an SMF for the SM message, according tosome embodiments.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. QQ1.For simplicity, the wireless network of FIG. QQ1 only depicts networkQQ106, network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, andQQ110 c. In practice, a wireless network may further include anyadditional elements suitable to support communication between wirelessdevices or between a wireless device and another communication device,such as a landline telephone, a service provider, or any other networknode or end device. Of the illustrated components, network node QQ160and wireless device (WD) QQ110 are depicted with additional detail. Thewireless network may provide communication and other types of servicesto one or more wireless devices to facilitate the wireless devices'access to and/or use of the services provided by, or via, the wirelessnetwork.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. QQ1, network node QQ160 includes processing circuitry QQ170,device readable medium QQ180, interface QQ190, auxiliary equipmentQQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.Although network node QQ160 illustrated in the example wireless networkof FIG. QQ1 may represent a device that includes the illustratedcombination of hardware components, other embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions and methods disclosed herein. Moreover, while the componentsof network node QQ160 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., device readable medium QQ180 maycomprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node QQ160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium QQ180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna QQ162 may be shared by the RATs). Network node QQ160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node QQ160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node QQ160.

Processing circuitry QQ170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry QQ170 may include processinginformation obtained by processing circuitry QQ170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode QQ160 components, such as device readable medium QQ180, networknode QQ160 functionality. For example, processing circuitry QQ170 mayexecute instructions stored in device readable medium QQ180 or in memorywithin processing circuitry QQ170. Such functionality may includeproviding any of the various wireless features, functions, or benefitsdiscussed herein. In some embodiments, processing circuitry QQ170 mayinclude a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or moreof radio frequency (RF) transceiver circuitry QQ172 and basebandprocessing circuitry QQ174. In some embodiments, radio frequency (RF)transceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180 or memorywithin processing circuitry QQ170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry QQ170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry QQ170 alone or toother components of network node QQ160, but are enjoyed by network nodeQQ160 as a whole, and/or by end users and the wireless networkgenerally.

Device readable medium QQ180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry QQ170. Device readable medium QQ180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ170 and, utilized by network node QQ160.Device readable medium QQ180 may be used to store any calculations madeby processing circuitry QQ170 and/or any data received via interfaceQQ190. In some embodiments, processing circuitry QQ170 and devicereadable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication ofsignalling and/or data between network node QQ160, network QQ106, and/orWDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s)QQ194 to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190 also includes radio front endcircuitry QQ192 that may be coupled to, or in certain embodiments a partof, antenna QQ162. Radio front end circuitry QQ192 comprises filtersQQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may beconnected to antenna QQ162 and processing circuitry QQ170. Radio frontend circuitry may be configured to condition signals communicatedbetween antenna QQ162 and processing circuitry QQ170. Radio front endcircuitry QQ192 may receive digital data that is to be sent out to othernetwork nodes or WDs via a wireless connection. Radio front endcircuitry QQ192 may convert the digital data into a radio signal havingthe appropriate channel and bandwidth parameters using a combination offilters QQ198 and/or amplifiers QQ196. The radio signal may then betransmitted via antenna QQ162. Similarly, when receiving data, antennaQQ162 may collect radio signals which are then converted into digitaldata by radio front end circuitry QQ192. The digital data may be passedto processing circuitry QQ170. In other embodiments, the interface maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, network node QQ160 may not includeseparate radio front end circuitry QQ192, instead, processing circuitryQQ170 may comprise radio front end circuitry and may be connected toantenna QQ162 without separate radio front end circuitry QQ192.Similarly, in some embodiments, all or some of RF transceiver circuitryQQ172 may be considered a part of interface QQ190. In still otherembodiments, interface QQ190 may include one or more ports or terminalsQQ194, radio front end circuitry QQ192, and RF transceiver circuitryQQ172, as part of a radio unit (not shown), and interface QQ190 maycommunicate with baseband processing circuitry QQ174, which is part of adigital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna QQ162 may becoupled to radio front end circuitry QQ190 and may be any type ofantenna capable of transmitting and receiving data and/or signalswirelessly. In some embodiments, antenna QQ162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antennaQQ162 may be separate from network node QQ160 and may be connectable tonetwork node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network nodeQQ160 with power for performing the functionality described herein.Power circuitry QQ187 may receive power from power source QQ186. Powersource QQ186 and/or power circuitry QQ187 may be configured to providepower to the various components of network node QQ160 in a form suitablefor the respective components (e.g., at a voltage and current levelneeded for each respective component). Power source QQ186 may either beincluded in, or external to, power circuitry QQ187 and/or network nodeQQ160. For example, network node QQ160 may be connectable to an externalpower source (e.g., an electricity outlet) via an input circuitry orinterface such as an electrical cable, whereby the external power sourcesupplies power to power circuitry QQ187. As a further example, powersource QQ186 may comprise a source of power in the form of a battery orbattery pack which is connected to, or integrated in, power circuitryQQ187. The battery may provide backup power should the external powersource fail. Other types of power sources, such as photovoltaic devices,may also be used.

Alternative embodiments of network node QQ160 may include additionalcomponents beyond those shown in FIG. QQ1 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node QQ160 may include user interface equipment to allow inputof information into network node QQ160 and to allow output ofinformation from network node QQ160. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions fornetwork node QQ160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interfaceQQ114, processing circuitry QQ120, device readable medium QQ130, userinterface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface QQ114. In certain alternative embodiments, antenna QQ111 maybe separate from WD QQ110 and be connectable to WD QQ110 through aninterface or port. Antenna QQ111, interface QQ114, and/or processingcircuitry QQ120 may be configured to perform any receiving ortransmitting operations described herein as being performed by a WD. Anyinformation, data and/or signals may be received from a network nodeand/or another WD. In some embodiments, radio front end circuitry and/orantenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitryQQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one ormore filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111 and processing circuitry QQ120, and isconfigured to condition signals communicated between antenna QQ111 andprocessing circuitry QQ120. Radio front end circuitry QQ112 may becoupled to or a part of antenna QQ111. In some embodiments, WD QQ110 maynot include separate radio front end circuitry QQ112; rather, processingcircuitry QQ120 may comprise radio front end circuitry and may beconnected to antenna QQ111. Similarly, in some embodiments, some or allof RF transceiver circuitry QQ122 may be considered a part of interfaceQQ114. Radio front end circuitry QQ112 may receive digital data that isto be sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry QQ112 may convert the digital data into aradio signal having the appropriate channel and bandwidth parametersusing a combination of filters QQ118 and/or amplifiers QQ116. The radiosignal may then be transmitted via antenna QQ111. Similarly, whenreceiving data, antenna QQ111 may collect radio signals which are thenconverted into digital data by radio front end circuitry QQ112. Thedigital data may be passed to processing circuitry QQ120. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of thevarious wireless features or benefits discussed herein. For example,processing circuitry QQ120 may execute instructions stored in devicereadable medium QQ130 or in memory within processing circuitry QQ120 toprovide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitryQQ120 of WD QQ110 may comprise a SOC. In some embodiments, RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be on separate chips or setsof chips. In alternative embodiments, part or all of baseband processingcircuitry QQ124 and application processing circuitry QQ126 may becombined into one chip or set of chips, and RF transceiver circuitryQQ122 may be on a separate chip or set of chips. In still alternativeembodiments, part or all of RF transceiver circuitry QQ122 and basebandprocessing circuitry QQ124 may be on the same chip or set of chips, andapplication processing circuitry QQ126 may be on a separate chip or setof chips. In yet other alternative embodiments, part or all of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be combined in the same chipor set of chips. In some embodiments, RF transceiver circuitry QQ122 maybe a part of interface QQ114. RF transceiver circuitry QQ122 maycondition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry QQ120 executing instructions stored on device readable mediumQQ130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry QQ120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry QQ120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry QQ120 alone or to other componentsof WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end usersand the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry QQ120, may include processinginformation obtained by processing circuitry QQ120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD QQ110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium QQ130 may be operable to store a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ120. Device readable medium QQ130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ120. In someembodiments, processing circuitry QQ120 and device readable medium QQ130may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for ahuman user to interact with WD QQ110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipmentQQ132 may be operable to produce output to the user and to allow theuser to provide input to WD QQ110. The type of interaction may varydepending on the type of user interface equipment QQ132 installed in WDQQ110. For example, if WD QQ110 is a smart phone, the interaction may bevia a touch screen; if WD QQ110 is a smart meter, the interaction may bethrough a screen that provides usage (e.g., the number of gallons used)or a speaker that provides an audible alert (e.g., if smoke isdetected). User interface equipment QQ132 may include input interfaces,devices and circuits, and output interfaces, devices and circuits. Userinterface equipment QQ132 is configured to allow input of informationinto WD QQ110, and is connected to processing circuitry QQ120 to allowprocessing circuitry QQ120 to process the input information. Userinterface equipment QQ132 may include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a USB port, or other input circuitry. User interface equipmentQQ132 is also configured to allow output of information from WD QQ110,and to allow processing circuitry QQ120 to output information from WDQQ110. User interface equipment QQ132 may include, for example, aspeaker, a display, vibrating circuitry, a USB port, a headphoneinterface, or other output circuitry. Using one or more input and outputinterfaces, devices, and circuits, of user interface equipment QQ132, WDQQ110 may communicate with end users and/or the wireless network, andallow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD QQ110 may further comprise power circuitryQQ137 for delivering power from power source QQ136 to the various partsof WD QQ110 which need power from power source QQ136 to carry out anyfunctionality described or indicated herein. Power circuitry QQ137 mayin certain embodiments comprise power management circuitry. Powercircuitry QQ137 may additionally or alternatively be operable to receivepower from an external power source; in which case WD QQ110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry QQ137 may also in certain embodiments be operable todeliver power from an external power source to power source QQ136. Thismay be, for example, for the charging of power source QQ136. Powercircuitry QQ137 may perform any formatting, converting, or othermodification to the power from power source QQ136 to make the powersuitable for the respective components of WD QQ110 to which power issupplied.

FIG. QQ2 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE QQ2200 may be any UE identifiedby the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE,a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE QQ200, as illustrated in FIG. QQ2, is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3rd Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG.QQ2 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. QQ2, UE QQ200 includes processing circuitry QQ201 that isoperatively coupled to input/output interface QQ205, radio frequency(RF) interface QQ209, network connection interface QQ211, memory QQ215including random access memory (RAM) QQ217, read-only memory (ROM)QQ219, and storage medium QQ221 or the like, communication subsystemQQ231, power source QQ233, and/or any other component, or anycombination thereof. Storage medium QQ221 includes operating systemQQ223, application program QQ225, and data QQ227. In other embodiments,storage medium QQ221 may include other similar types of information.Certain UEs may utilize all of the components shown in FIG. QQ2, or onlya subset of the components. The level of integration between thecomponents may vary from one UE to another UE. Further, certain UEs maycontain multiple instances of a component, such as multiple processors,memories, transceivers, transmitters, receivers, etc.

In FIG. QQ2, processing circuitry QQ201 may be configured to processcomputer instructions and data. Processing circuitry QQ201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry QQ201 may includetwo central processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE QQ200 may be configured touse an output device via input/output interface QQ205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE QQ200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE QQ200 may be configured to use aninput device via input/output interface QQ205 to allow a user to captureinformation into UE QQ200. The input device may include atouch-sensitive or presence-sensitive display, a camera (e.g., a digitalcamera, a digital video camera, a web camera, etc.), a microphone, asensor, a mouse, a trackball, a directional pad, a trackpad, a scrollwheel, a smartcard, and the like. The presence-sensitive display mayinclude a capacitive or resistive touch sensor to sense input from auser. A sensor may be, for instance, an accelerometer, a gyroscope, atilt sensor, a force sensor, a magnetometer, an optical sensor, aproximity sensor, another like sensor, or any combination thereof. Forexample, the input device may be an accelerometer, a magnetometer, adigital camera, a microphone, and an optical sensor.

In FIG. QQ2, RF interface QQ209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface QQ211 may beconfigured to provide a communication interface to network QQ243 a.Network QQ243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network QQ243 a may comprise aWi-Fi network. Network connection interface QQ211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface QQ211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processingcircuitry QQ201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processingcircuitry QQ201. For example, ROM QQ219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage mediumQQ221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium QQ221 may be configured toinclude operating system QQ223, application program QQ225 such as a webbrowser application, a widget or gadget engine or another application,and data file QQ227. Storage medium QQ221 may store, for use by UEQQ200, any of a variety of various operating systems or combinations ofoperating systems.

Storage medium QQ221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium QQ221 may allow UE QQ200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium QQ221, which may comprise adevice readable medium.

In FIG. QQ2, processing circuitry QQ201 may be configured to communicatewith network QQ243 b using communication subsystem QQ231. Network QQ243a and network QQ243 b may be the same network or networks or differentnetwork or networks. Communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.QQ2,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter QQ233 and/or receiver QQ235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem QQ231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem QQ231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network QQ243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, networkQQ243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source QQ213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE QQ200 or partitioned acrossmultiple components of UE QQ200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystemQQ231 may be configured to include any of the components describedherein. Further, processing circuitry QQ201 may be configured tocommunicate with any of such components over bus QQ202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitryQQ201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry QQ201 and communication subsystem QQ231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. QQ3 is a schematic block diagram illustrating a virtualizationenvironment QQ300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments QQ300 hosted byone or more of hardware nodes QQ330. Further, in embodiments in whichthe virtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions,etc.) operative to implement some of the features, functions, and/orbenefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300 which provides hardwareQQ330 comprising processing circuitry QQ360 and memory QQ390. MemoryQQ390 contains instructions QQ395 executable by processing circuitryQQ360 whereby application QQ320 is operative to provide one or more ofthe features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose orspecial-purpose network hardware devices QQ330 comprising a set of oneor more processors or processing circuitry QQ360, which may becommercial off-the-shelf (COTS) processors, dedicated ApplicationSpecific Integrated Circuits (ASICs), or any other type of processingcircuitry including digital or analog hardware components or specialpurpose processors. Each hardware device may comprise memory QQ390-1which may be non-persistent memory for temporarily storing instructionsQQ395 or software executed by processing circuitry QQ360. Each hardwaredevice may comprise one or more network interface controllers (NICs)QQ370, also known as network interface cards, which include physicalnetwork interface QQ380. Each hardware device may also includenon-transitory, persistent, machine-readable storage media QQ390-2having stored therein software QQ395 and/or instructions executable byprocessing circuitry QQ360. Software QQ395 may include any type ofsoftware including software for instantiating one or more virtualizationlayers QQ350 (also referred to as hypervisors), software to executevirtual machines QQ340 as well as software allowing it to executefunctions, features and/or benefits described in relation with someembodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer QQ350 or hypervisor. Differentembodiments of the instance of virtual appliance QQ320 may beimplemented on one or more of virtual machines QQ340, and theimplementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 toinstantiate the hypervisor or virtualization layer QQ350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer QQ350 may present a virtual operating platform thatappears like networking hardware to virtual machine QQ340.

As shown in FIG. QQ3, hardware QQ330 may be a standalone network nodewith generic or specific components. Hardware QQ330 may comprise antennaQQ3225 and may implement some functions via virtualization.Alternatively, hardware QQ330 may be part of a larger cluster ofhardware (e.g. such as in a data center or customer premise equipment(CPE)) where many hardware nodes work together and are managed viamanagement and orchestration (MANO) QQ3100, which, among others,oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines QQ340, and that part of hardware QQ330 that executes thatvirtual machine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines QQ340 on top of hardware networking infrastructureQQ330 and corresponds to application QQ320 in FIG. QQ3.

In some embodiments, one or more radio units QQ3200 that each includeone or more transmitters QQ3220 and one or more receivers QQ3210 may becoupled to one or more antennas QQ3225. Radio units QQ3200 maycommunicate directly with hardware nodes QQ330 via one or moreappropriate network interfaces and may be used in combination with thevirtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system QQ3230 which may alternatively be used for communicationbetween the hardware nodes QQ330 and radio units QQ3200.

With reference to FIG. QQ4, a communication system in accordance with anembodiment is shown. The illustrated communication system includestelecommunication network QQ410, such as a 3GPP-type cellular network,which comprises access network QQ411, such as a radio access network,and core network QQ414. Access network QQ411 comprises a plurality ofbase stations QQ412 a, QQ412 b, QQ412 c, such as NBs, eNBs, gNBs orother types of wireless access points, each defining a correspondingcoverage area QQ413 a, QQ413 b, QQ413 c. Each base station QQ412 a,QQ412 b, QQ412 c is connectable to core network QQ414 over a wired orwireless connection QQ415. A first UE QQ491 located in coverage areaQQ413 c is configured to wirelessly connect to, or be paged by, thecorresponding base station QQ412 c. A second UE QQ492 in coverage areaQQ413 a is wirelessly connectable to the corresponding base stationQQ412 a. While a plurality of UEs QQ491, QQ492 are illustrated in thisexample, the disclosed embodiments are equally applicable to a situationwhere a sole UE is in the coverage area or where a sole UE is connectingto the corresponding base station QQ412.

Telecommunication network QQ410 is itself connected to host computerQQ430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer QQ430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections QQ421 and QQ422 between telecommunication network QQ410 andhost computer QQ430 may extend directly from core network QQ414 to hostcomputer QQ430 or may go via an optional intermediate network QQ420.Intermediate network QQ420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network QQ420,if any, may be a backbone network or the Internet; in particular,intermediate network QQ420 may comprise two or more sub-networks (notshown).

The communication system of FIG. QQ4 as a whole enables connectivitybetween the connected UEs QQ491, QQ492 and host computer QQ430. Theconnectivity may be described as an over-the-top (OTT) connection QQ450.Host computer QQ430 and the connected UEs QQ491, QQ492 are configured tocommunicate data and/or signaling via OTT connection QQ450, using accessnetwork QQ411, core network QQ414, any intermediate network QQ420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection QQ450 may be transparent in the sense that the participatingcommunication devices through which OTT connection QQ450 passes areunaware of routing of uplink and downlink communications. For example,base station QQ412 may not or need not be informed about the pastrouting of an incoming downlink communication with data originating fromhost computer QQ430 to be forwarded (e.g., handed over) to a connectedUE QQ491. Similarly, base station QQ412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UEQQ491 towards the host computer QQ430.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. QQ5. In communicationsystem QQ500, host computer QQ510 comprises hardware QQ515 includingcommunication interface QQ516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system QQ500. Host computer QQ510 furthercomprises processing circuitry QQ518, which may have storage and/orprocessing capabilities. In particular, processing circuitry QQ518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer QQ510further comprises software QQ511, which is stored in or accessible byhost computer QQ510 and executable by processing circuitry QQ518.Software QQ511 includes host application QQ512. Host application QQ512may be operable to provide a service to a remote user, such as UE QQ530connecting via OTT connection QQ550 terminating at UE QQ530 and hostcomputer QQ510. In providing the service to the remote user, hostapplication QQ512 may provide user data which is transmitted using OTTconnection QQ550.

Communication system QQ500 further includes base station QQ520 providedin a telecommunication system and comprising hardware QQ525 enabling itto communicate with host computer QQ510 and with UE QQ530. HardwareQQ525 may include communication interface QQ526 for setting up andmaintaining a wired or wireless connection with an interface of adifferent communication device of communication system QQ500, as well asradio interface QQ527 for setting up and maintaining at least wirelessconnection QQ570 with UE QQ530 located in a coverage area (not shown inFIG. QQ5) served by base station QQ520. Communication interface QQ526may be configured to facilitate connection QQ560 to host computer QQ510.Connection QQ560 may be direct or it may pass through a core network(not shown in FIG. QQ5) of the telecommunication system and/or throughone or more intermediate networks outside the telecommunication system.In the embodiment shown, hardware QQ525 of base station QQ520 furtherincludes processing circuitry QQ528, which may comprise one or moreprogrammable processors, application-specific integrated circuits, fieldprogrammable gate arrays or combinations of these (not shown) adapted toexecute instructions. Base station QQ520 further has software QQ521stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referredto. Its hardware QQ535 may include radio interface QQ537 configured toset up and maintain wireless connection QQ570 with a base stationserving a coverage area in which UE QQ530 is currently located. HardwareQQ535 of UE QQ530 further includes processing circuitry QQ538, which maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. UE QQ530 furthercomprises software QQ531, which is stored in or accessible by UE QQ530and executable by processing circuitry QQ538. Software QQ531 includesclient application QQ532. Client application QQ532 may be operable toprovide a service to a human or non-human user via UE QQ530, with thesupport of host computer QQ510. In host computer QQ510, an executinghost application QQ512 may communicate with the executing clientapplication QQ532 via OTT connection QQ550 terminating at UE QQ530 andhost computer QQ510. In providing the service to the user, clientapplication QQ532 may receive request data from host application QQ512and provide user data in response to the request data. OTT connectionQQ550 may transfer both the request data and the user data. Clientapplication QQ532 may interact with the user to generate the user datathat it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530illustrated in FIG. QQ5 may be similar or identical to host computerQQ430, one of base stations QQ412 a, QQ412 b, QQ412 c and one of UEsQQ491, QQ492 of FIG. QQ4, respectively. This is to say, the innerworkings of these entities may be as shown in FIG. QQ5 andindependently, the surrounding network topology may be that of FIG. QQ4.

In FIG. QQ5, OTT connection QQ550 has been drawn abstractly toillustrate the communication between host computer QQ510 and UE QQ530via base station QQ520, without explicit reference to any intermediarydevices and the precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE QQ530 or from the service provider operating host computerQQ510, or both. While OTT connection QQ550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE QQ530 using OTT connectionQQ550, in which wireless connection QQ570 forms the last segment. Moreprecisely, the teachings of these embodiments improve the handling of SMmessages (e.g., 5GSM messages) transmitted by a UE when a AMF fails toforward a SM message transmitted by the UE to a SMF. Specifically, theteachings of these embodiments allow the AMF to notify the UE regardingthe failure to forward the SM message to a SMF by creating a statusmessage (5GMM STATUS message) comprising the SM message and transmittingthe status message to the UE. Upon receipt of the status message, the UEdetermines that the AMF has failed to forward the SM message, therebypreventing the UE from sending the same SM message to the AMF whichwould result in the same failure.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection QQ550 between hostcomputer QQ510 and UE QQ530, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring OTT connection QQ550 may be implementedin software QQ511 and hardware QQ515 of host computer QQ510 or insoftware QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection QQ550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above, or supplying values ofother physical quantities from which software QQ511, QQ531 may computeor estimate the monitored quantities. The reconfiguring of OTTconnection QQ550 may include message format, retransmission settings,preferred routing etc.; the reconfiguring need not affect base stationQQ520, and it may be unknown or imperceptible to base station QQ520.Such procedures and functionalities may be known and practiced in theart. In certain embodiments, measurements may involve proprietary UEsignaling facilitating host computer QQ510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software QQ511 and QQ531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection QQ550 while it monitors propagation times, errors etc.

FIG. QQ6 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG.QQ6 will be included in this section. In step QQ610, the host computerprovides user data. In substep QQ611 (which may be optional) of stepQQ610, the host computer provides the user data by executing a hostapplication. In step QQ620, the host computer initiates a transmissioncarrying the user data to the UE. In step QQ630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step QQ640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. QQ7 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG.QQ7 will be included in this section. In step QQ710 of the method, thehost computer provides user data. In an optional substep (not shown) thehost computer provides the user data by executing a host application. Instep QQ720, the host computer initiates a transmission carrying the userdata to the UE. The transmission may pass via the base station, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In step QQ730 (which may be optional), the UE receivesthe user data carried in the transmission.

FIG. QQ8 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG.QQ8 will be included in this section. In step QQ810 (which may beoptional), the UE receives input data provided by the host computer.Additionally or alternatively, in step QQ820, the UE provides user data.In substep QQ821 (which may be optional) of step QQ820, the UE providesthe user data by executing a client application. In substep QQ811 (whichmay be optional) of step QQ810, the UE executes a client applicationwhich provides the user data in reaction to the received input dataprovided by the host computer. In providing the user data, the executedclient application may further consider user input received from theuser. Regardless of the specific manner in which the user data wasprovided, the UE initiates, in substep QQ830 (which may be optional),transmission of the user data to the host computer. In step QQ840 of themethod, the host computer receives the user data transmitted from theUE, in accordance with the teachings of the embodiments describedthroughout this disclosure.

FIG. QQ9 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG.QQ9 will be included in this section. In step QQ910 (which may beoptional), in accordance with the teachings of the embodiments describedthroughout this disclosure, the base station receives user data from theUE. In step QQ920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In stepQQ930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

FIG. VV1 depicts a method VV100, in accordance with particularembodiments, that is performed by a wireless device. Method VV100 maybegin at step VV102 in which the wireless device transmits a transportmessage (e.g., UL SM Message Transport message) to an Access andMobility Function (AMF), wherein the transport message comprises a SMmessage (e.g., 5GSM message). In some embodiments, the transport messagemay further comprise at least one or more of: a protocol data unit (PDU)session identifier (ID), a data network name (DNN), and a request typeindication. In some embodiments, the SM message may comprise a proceduretransaction identity (PTI) indication identifying a session managementtransaction (e.g., 5GSM transaction) associated with the SM message.

At step VV104, the wireless device receives a status message (e.g., 5GMMStatus message) transmitted by the AMF, wherein the status messagecomprises at least a portion of the transport message and an indicationof non-delivery of the SM message to a SMF. In such an embodiments, theportion of the transport message comprises the SM message. In someembodiments, the indication of non-delivery may comprise a cause offailure to deliver the SM message to a SMF.

In some embodiments, the SM message may be one of: (i) a sessionestablishment request message (e.g., PDU Session Establishment Requestmessage), (ii) a session modification request message (e.g., PDU SessionModification Request message), and (iii) a session release requestmessage (e.g., PDU Session Release Request message). In such anembodiment, the method VV100 may further include the wireless devicestopping a timer (e.g., Tx, Tk or Tz) as a result of receiving theindication of non-delivery. In such an embodiment, the method VV100 mayfurther include determining that a session associated with the SMmessage is: (i) not established, (ii) not modified or (iii) notreleased.

FIG. VV2 depicts a method VV200, in accordance with particularembodiments, that is performed by an Access and Mobility ManagementFunction (AMF). Method VV200 may begin at step VV202 in which the AMFreceives a transport message (e.g., UL SM Message Transport message)transmitted by a wireless device, wherein the transport messagecomprises a SM message (e.g., 5GSM message). In some embodiments, the SMmessage may comprise a procedure transaction identity (PTI) indicationidentifying a session management transaction (e.g., 5GSM transaction)associated with the SM message. In some embodiments, the transportmessage may further comprise at least one or more of: a protocol dataunit (PDU) session identifier (ID), a data network name (DNN), and arequest type indication.

At step VV204, the AMF determines, based on the transport message,whether the SM message can be forwarded to a SMF.

In some embodiments, the step VV204 of determining, based on thetransport message, whether the SM message can be forwarded to a SMF mayfurther comprise: the AMF determining whether the AMF has a PDU sessionrouting context for the PDU session identifier, wherein the request typeindication indicates that the SM message is associated to an initialrequest; and as a result of determining that the AMF does not have a PDUsession routing context for the PDU session identifier, the AMFdetermining that a SMF cannot be selected for the SM message.

In some embodiments, the step VV204 of determining, based on thetransport message, whether the SM message can be forwarded to a SMF mayfurther comprise: the AMF determining whether the AMF has a PDU sessionrouting context for the PDU session identifier, wherein the request typeindication indicates that the SM message is associated to an existingPDU session; the AMF obtaining subscription context for the wirelessdevice from a unified data management (UDM), wherein the subscriptioncontext comprises at least one or more SMF identifier (ID); and as aresult of determining: (i) that the AMF does not have a PDU sessionrouting context for the PDU session identifier and (ii) the at least oneor more SMF ID is not associated with the DNN, the AMF determining thata SMF cannot be selected for the SM message.

In some embodiments, the step VV204 of determining, based on thetransport message, whether the SM message can be forwarded to a SMF mayfurther comprise: the AMF determining whether the AMF has a PDU sessionrouting context for the PDU session identifier, wherein the request typeindication indicates that the SM message is associated to an existingPDU session, and the DNN is not included in the transport message; theAMF obtaining subscription context for the wireless device from aunified data management (UDM), wherein the subscription contextcomprises at least one or more SMF identifier (ID); and as a result ofdetermining: (i) that the AMF does not have a PDU session routingcontext for the PDU session identifier and (ii) the at least one or moreSMF ID is not associated with a default DNN, the AMF determining that aSMF cannot be selected for the SM message.

In some embodiments, the step VV204 of determining, based on thetransport message, whether the SM message can be forwarded to a SMF mayfurther comprise: the AMF determining whether the AMF has a PDU sessionrouting context for the PDU session identifier, wherein the request typeindication is not included in the transport message; and as a result ofdetermining that the AMF does not have a PDU session routing context forthe PDU session identifier, the AMF determining that a SMF cannot beselected for the SM message.

At step VV206, as a result of determining that the SM message cannot beforwarded to a SMF, the AMF creates a status message (e.g., 5GMM Statusmessage) comprising at least a portion of the transport message and anindication of non-delivery of the SM message to a SMF. In someembodiments, the indication of non-delivery comprises a cause of failureto deliver the SM message to a SMF. In some embodiments, the portion ofthe transport message comprises the SM message.

At step VV 208, the AMF transmits the status message to the wirelessdevice.

FIG. WW1 illustrates a schematic block diagram of an apparatus WW100 ina wireless network (for example, the wireless network shown in FIG.QQ1). The apparatus may be implemented in a wireless device or networknode (e.g., wireless device QQ110 or network node QQ160 shown in FIG.QQ1). Apparatus WW100 is operable to carry out the example methoddescribed with reference to FIG. VV1 and possibly any other processes ormethods disclosed herein. It is also to be understood that the method ofFIG. VV1 is not necessarily carried out solely by apparatus WW100. Atleast some operations of the method can be performed by one or moreother entities.

Virtual Apparatus WW100 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to causetransmitter unit WW102 to transmit a transport message (e.g., UL SMMessage Transport message) to an Access and Mobility Function (AMF),wherein the transport message comprises a SM message (e.g., 5GSMmessage), receiver unit WW104 to receive a status message (e.g., 5GMMStatus message) transmitted by the AMF, wherein the status messagecomprises at least a portion of the transport message and an indicationof non-delivery of the SM message to a SMF, and any other suitable unitsof apparatus WW100 to perform corresponding functions according one ormore embodiments of the present disclosure.

As illustrated in FIG. WW1, apparatus WW100 includes a transmitter unitWW102 configured to transmit a transport message (e.g., UL SM MessageTransport message) to an Access and Mobility Function (AMF), wherein thetransport message comprises a SM message (e.g., 5GSM message), and areceiver unit WW104 configured to receive a status message (e.g., 5GMMStatus message) transmitted by the AMF, wherein the status messagecomprises at least a portion of the transport message and an indicationof non-delivery of the SM message to a SMF.

FIG. WW2 illustrates a schematic block diagram of an apparatus WW200 ina wireless network (for example, the wireless network shown in FIG.QQ1). The apparatus may be implemented in a wireless device or networknode (e.g., wireless device QQ110 or network node QQ160 shown in FIG.QQ1). Apparatus WW200 is operable to carry out the example methoddescribed with reference to FIG. VV2 and possibly any other processes ormethods disclosed herein. It is also to be understood that the method ofFIG. VV2 is not necessarily carried out solely by apparatus WW200. Atleast some operations of the method can be performed by one or moreother entities.

Virtual Apparatus WW200 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to cause receiverunit WW202 to receive a transport message (e.g., UL SM Message Transportmessage) transmitted by a wireless device, wherein the transport messagecomprises a SM message (e.g., 5GSM message), determining unit WW204 todetermine, based on the transport message, whether the SM message can beforwarded to a SMF, creating unit WW206 to create a status message(e.g., 5GMM Status message) comprising at least a portion of thetransport message and an indication of non-delivery of the SM message toa SMF as a result of determining that the SM message cannot be forwardedto a SMF, transmitter unit WW208 to transmit the status message to thewireless device, and any other suitable units of apparatus WW200 toperform corresponding functions according one or more embodiments of thepresent disclosure.

As illustrated in FIG. WW2, apparatus WW200 includes a receiver unitWW202 configured to receive a transport message (e.g., UL SM MessageTransport message) transmitted by a wireless device, wherein thetransport message comprises a SM message (e.g., 5GSM message), adetermining unit WW204 configured to determine, based on the transportmessage, whether the SM message can be forwarded to a SMF, a creatingunit WW206 to create a status message (e.g., 5GMM Status message)comprising at least a portion of the transport message and an indicationof non-delivery of the SM message to a SMF as a result of determiningthat the SM message cannot be forwarded to a SMF, and a transmitter unitWW208 configured to transmit the status message to the wireless device.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

EMBODIMENTS Group A Embodiments—UE

A1. A method implemented in a wireless device, comprising:

transmitting a transport message (e.g., UL SM Message Transport message)to an Access and Mobility Function (AMF), wherein the transport messagecomprises a SM message (e.g., 5GSM message); and

receiving a status message (e.g., 5GMM Status message) transmitted bythe AMF, wherein the status message comprises at least a portion of thetransport message and an indication of non-delivery of the SM message toa SMF.

A2. The method of A1, wherein the portion of the transport messagecomprises the SM message.

A3. The method of A1 or A2, wherein the transport message furthercomprises at least one or more of: a protocol data unit (PDU) sessionidentifier (ID), a data network name (DNN), and a request typeindication.

A4. The method of any one of A1-A3, wherein the SM message comprises aprocedure transaction identity (PTI) indication identifying a sessionmanagement transaction (e.g., 5GSM transaction) associated with the SMmessage.

A5. The method of any one of A1-A4, wherein the SM message is one of:(i) a session establishment request message (e.g., PDU SessionEstablishment Request message), (ii) a session modification requestmessage (e.g., PDU Session Modification Request message), and (iii) asession release request message (e.g., PDU Session Release Requestmessage), the method further comprising:

as a result of receiving the indication of non-delivery, stopping atimer (e.g., Tx, Tk or Tz).

A6. The method of A5, the method further comprising:

as a result of receiving the indication of non-delivery, determiningthat a session associated with the SM message is: (i) not established,(ii) not modified or (iii) not released.

A7. The method of any one of A1-A6, wherein the indication ofnon-delivery comprises a cause of failure to deliver the SM message to aSMF.

A8. The method of any of the previous embodiments, further comprising:

providing user data; and

forwarding the user data to a host computer via the transmission to thebase station.

Group B Embodiments—Base Station

B1. A method performed by an Access and Mobility Management Function(AMF), comprising:

receiving a transport message (e.g., UL SM Message Transport message)transmitted by a wireless device, wherein the transport messagecomprises a SM message (e.g., 5GSM message);

determining, based on the transport message, whether the SM message canbe forwarded to a SMF;

as a result of determining that the SM message cannot be forwarded to aSMF, creating a status message (e.g., 5GMM Status message) comprising atleast a portion of the transport message and an indication ofnon-delivery of the SM message to a SMF; and

transmitting the status message to the wireless device.

B2. The method of B1, wherein the portion of the transport messagecomprises the SM message.

B3. The method of B1 or B2, wherein the SM message comprises a proceduretransaction identity (PTI) indication identifying a session managementtransaction (e.g., 5GSM transaction) associated with the SM message.

B4. The method of any one of B1-B3, wherein the transport messagefurther comprises at least one or more of: a protocol data unit (PDU)session identifier (ID), a data network name (DNN), and a request typeindication.

B5. The method of B4, wherein the determining, based on the transportmessage, whether the SM message can be forwarded to a SMF furthercomprises:

determining whether the AMF has a PDU session routing context for thePDU session identifier, wherein the request type indication indicatesthat the SM message is associated to an initial request; and

as a result of determining that the AMF does not have a PDU sessionrouting context for the PDU session identifier, determining that a SMFcannot be selected for the SM message.

B6. The method of B4, wherein the determining, based on the transportmessage, whether the SM message can be forwarded to a SMF furthercomprises:

determining whether the AMF has a PDU session routing context for thePDU session identifier, wherein the request type indication indicatesthat the SM message is associated to an existing PDU session;

obtaining subscription context for the wireless device from a unifieddata management (UDM), wherein the subscription context comprises atleast one or more SMF identifier (ID); and

as a result of determining: (i) that the AMF does not have a PDU sessionrouting context for the PDU session identifier and (ii) the at least oneor more SMF ID is not associated with the DNN, determining that a SMFcannot be selected for the SM message.

B7. The method of B4, wherein the determining, based on the transportmessage, whether the SM message can be forwarded to a SMF furthercomprises:

determining whether the AMF has a PDU session routing context for thePDU session identifier, wherein the request type indication indicatesthat the SM message is associated to an existing PDU session, and theDNN is not included in the transport message;

obtaining subscription context for the wireless device from a unifieddata management (UDM), wherein the subscription context comprises atleast one or more SMF identifier (ID); and

as a result of determining: (i) that the AMF does not have a PDU sessionrouting context for the PDU session identifier and (ii) the at least oneor more SMF ID is not associated with a default DNN, determining that aSMF cannot be selected for the SM message.

B8. The method of B4, wherein the determining, based on the transportmessage, whether the SM message can be forwarded to a SMF furthercomprises:

determining whether the AMF has a PDU session routing context for thePDU session identifier, wherein the request type indication is notincluded in the transport message; and

as a result of determining that the AMF does not have a PDU sessionrouting context for the PDU session identifier, determining that a SMFcannot be selected for the SM message.

B9. The method of any one of B1-B8, wherein the indication ofnon-delivery comprises a cause of failure to deliver the SM message to aSMF.

B10. The method of any of the previous embodiments, further comprising:

obtaining user data; and

forwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1. A wireless device comprising:

processing circuitry configured to perform any of the steps of any ofthe Group A embodiments; and

power supply circuitry configured to supply power to the wirelessdevice.

C2. A base station, the base station comprising:

processing circuitry configured to perform any of the steps of any ofthe Group B embodiments;

power supply circuitry configured to supply power to the wirelessdevice.

C3. A user equipment (UE) comprising:

an antenna configured to send and receive wireless signals;

radio front-end circuitry connected to the antenna and to processingcircuitry, and configured to condition signals communicated between theantenna and the processing circuitry;

the processing circuitry being configured to perform any of the steps ofany of the Group A embodiments;

an input interface connected to the processing circuitry and configuredto allow input of information into the UE to be processed by theprocessing circuitry;

an output interface connected to the processing circuitry and configuredto output information from the UE that has been processed by theprocessing circuitry; and

a battery connected to the processing circuitry and configured to supplypower to the UE.

C4. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward the user data to acellular network for transmission to a user equipment (UE),

wherein the cellular network comprises a base station having a radiointerface and processing circuitry, the base station's processingcircuitry configured to perform any of the steps of any of the Group Bembodiments.

C5. The communication system of the pervious embodiment furtherincluding the base station.

C6. The communication system of the previous 2 embodiments, furtherincluding the UE, wherein the UE is configured to communicate with thebase station.

C7. The communication system of the previous 3 embodiments, wherein:

the processing circuitry of the host computer is configured to execute ahost application, thereby providing the user data; and

the UE comprises processing circuitry configured to execute a clientapplication associated with the host application.

C8. A method implemented in a communication system including a hostcomputer, a base station and a user equipment (UE), the methodcomprising:

at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user datato the UE via a cellular network comprising the base station, whereinthe base station performs any of the steps of any of the Group Bembodiments.

C9. The method of the previous embodiment, further comprising, at thebase station, transmitting the user data.

C10. The method of the previous 2 embodiments, wherein the user data isprovided at the host computer by executing a host application, themethod further comprising, at the UE, executing a client applicationassociated with the host application.

C11. A user equipment (UE) configured to communicate with a basestation, the UE comprising a radio interface and processing circuitryconfigured to performs the of the previous 3 embodiments.

C12. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward user data to a cellularnetwork for transmission to a user equipment (UE),

wherein the UE comprises a radio interface and processing circuitry, theUE's components configured to perform any of the steps of any of theGroup A embodiments.

C13. The communication system of the previous embodiment, wherein thecellular network further includes a base station configured tocommunicate with the UE.

C14. The communication system of the previous 2 embodiments, wherein:

the processing circuitry of the host computer is configured to execute ahost application, thereby providing the user data; and

the UE's processing circuitry is configured to execute a clientapplication associated with the host application.

C15. A method implemented in a communication system including a hostcomputer, a base station and a user equipment (UE), the methodcomprising:

at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user datato the UE via a cellular network comprising the base station, whereinthe UE performs any of the steps of any of the Group A embodiments.

C16. The method of the previous embodiment, further comprising at theUE, receiving the user data from the base station.

C17. A communication system including a host computer comprising:

communication interface configured to receive user data originating froma transmission from a user equipment (UE) to a base station,

wherein the UE comprises a radio interface and processing circuitry, theUE's processing circuitry configured to perform any of the steps of anyof the Group A embodiments.

C18. The communication system of the previous embodiment, furtherincluding the UE.

C19. The communication system of the previous 2 embodiments, furtherincluding the base station, wherein the base station comprises a radiointerface configured to communicate with the UE and a communicationinterface configured to forward to the host computer the user datacarried by a transmission from the UE to the base station.

C20. The communication system of the previous 3 embodiments, wherein:

the processing circuitry of the host computer is configured to execute ahost application; and

the UE's processing circuitry is configured to execute a clientapplication associated with the host application, thereby providing theuser data.

C21. The communication system of the previous 4 embodiments, wherein:

the processing circuitry of the host computer is configured to execute ahost application, thereby providing request data; and

the UE's processing circuitry is configured to execute a clientapplication associated with the host application, thereby providing theuser data in response to the request data.

C22. A method implemented in a communication system including a hostcomputer, a base station and a user equipment (UE), the methodcomprising:

at the host computer, receiving user data transmitted to the basestation from the UE, wherein the UE performs any of the steps of any ofthe Group A embodiments.

C23. The method of the previous embodiment, further comprising, at theUE, providing the user data to the base station.

C24. The method of the previous 2 embodiments, further comprising:

at the UE, executing a client application, thereby providing the userdata to be transmitted; and

at the host computer, executing a host application associated with theclient application.

C25. The method of the previous 3 embodiments, further comprising:

at the UE, executing a client application; and

at the UE, receiving input data to the client application, the inputdata being provided at the host computer by executing a host applicationassociated with the client application,

wherein the user data to be transmitted is provided by the clientapplication in response to the input data.

C26. A communication system including a host computer comprising acommunication interface configured to receive user data originating froma transmission from a user equipment (UE) to a base station, wherein thebase station comprises a radio interface and processing circuitry, thebase station's processing circuitry configured to perform any of thesteps of any of the Group B embodiments.

C27. The communication system of the previous embodiment furtherincluding the base station.

C28. The communication system of the previous 2 embodiments, furtherincluding the UE, wherein the UE is configured to communicate with thebase station.

C29. The communication system of the previous 3 embodiments, wherein:

the processing circuitry of the host computer is configured to execute ahost application;

the UE is configured to execute a client application associated with thehost application, thereby providing the user data to be received by thehost computer.

C30. A method implemented in a communication system including a hostcomputer, a base station and a user equipment (UE), the methodcomprising:

at the host computer, receiving, from the base station, user dataoriginating from a transmission which the base station has received fromthe UE, wherein the UE performs any of the steps of any of the Group Aembodiments.

C31. The method of the previous embodiment, further comprising at thebase station, receiving the user data from the UE.

C32. The method of the previous 2 embodiments, further comprising at thebase station, initiating a transmission of the received user data to thehost computer.

While various embodiments of the present disclosure are described herein(including the attached appendix), it should be understood that theyhave been presented by way of example only, and not limitation. Thus,the breadth and scope of the present disclosure should not be limited byany of the above described exemplary embodiments. Moreover, anycombination of the above-described elements in all possible variationsthereof is encompassed by the disclosure unless otherwise indicatedherein or otherwise clearly contradicted by context.

Additionally, while the processes described above and illustrated in thedrawings are shown as a sequence of steps, this was done solely for thesake of illustration. Accordingly, it is contemplated that some stepsmay be added, some steps may be omitted, the order of the steps may bere-arranged, and some steps may be performed in parallel.

APPENDIX 2. Reason for Change 2.1 Problem Description

TR 24.890 contains the following editor's notes:8.5.1.1.2.1.1.4 Abnormal cases on the network side--------------The following abnormal cases in AMF are identified:

-   -   a) the AMF does not have a PDU session routing context for the        PDU session ID of the UL SM MESSAGE TRANSPORT message and the        UE, the request type IE of the UL SM MESSAGE TRANSPORT message        is set to “initial request”, and the SMF selection fails.    -   Editor's note: Handling of this abnormal case is FFS        --------------    -   b) the AMF does not have a PDU session routing context for the        PDU session ID of the UL SM MESSAGE TRANSPORT message and the        UE, the request type IE of the UL SM MESSAGE TRANSPORT message        is set to “existing PDU session”, and the user's subscription        context obtained from the UDM does not contain an SMF ID        corresponding to.        -   1) the DNN of the UL SM MESSAGE TRANSPORT message, if the            DNN is included in the NAS SM MESSAGE TRANSPORT message; or        -   2) the default DNN, if the DNN is not included in the UL SM            MESSAGE TRANSPORT message.    -   Editor's note: Handling of this abnormal case is FFS        . . .        Similar error can also occur when request type is not provided        by the UE.        If no handling is defined for the cases above, the failure is        due to a permanent cause (e.g. the requested DNN is not        authorized DNN for the UE) and the SM messages are        retransmitted, then the UE will retransmit the SM message in a        new UL SM MESSAGE TRANSPORT message and the AMF needs to repeat        the SMF selection again with the same failure.

2.2 Possible Solutions 2.2.1 Alternative-1

UE-initiated NAS transport procedure is extended with an UL SM MESSAGETRANSPORT ACCEPT message or an UL SM MESSAGE TRANSPORT REJECT message,which AMF sends upon reception and handling of UL SM MESSAGE TRANSPORTREQUEST message. Only up to one UE-initiated NAS transport procedurewould be run at any given time.If the AMF is able to forward 5GSM message of UL SM MESSAGE TRANSPORTREQUEST message, the AMF sends UL SM MESSAGE TRANSPORT ACCEPT message.If the AMF is unable to forward 5GSM message of UL SM MESSAGE TRANSPORTREQUEST message, the AMF sends UL SM MESSAGE TRANSPORT REJECT message.The UL SM MESSAGE TRANSPORT REJECT message contains a cause.As reliability is provided on SM transport layer, the 5GSM procedureswill not need to retransmit 5GSM messages.If transport of 5GSM message fails, the 5GSM procedure will consider the5GSM procedure as unsuccessfully completed.

2.2.2 Alternative-2

If the AMF is unable to forward 5GSM message of UL SM MESSAGE TRANSPORTmessage, the AMF sends 5GMM STATUS message. The 5GMM STATUS messagecontains a 5GMM message container IE containing the UL SM MESSAGETRANSPORT message, and a cause.If the UE receives a 5GMM STATUS message with 5GMM message container IEcontaining the UL SM MESSAGE TRANSPORT message containing a 5GSMmessage, the 5GMM layer informs the 5GSM layer about non-delivery of the5GSM message.Based on non-delivery of the 5GSM message, the 5GSM procedure will stopany retransmissions of the 5GSM message and consider the 5GSM procedureas unsuccessfully completed.

2.2.3 Alternative-3

AMF is configured with a SMF for rejection.AMF routes any SM message which is unable to route forward to the SMFfor rejection. The SMF rejects the 5GSM request message with appropriate5GSM response message.

2.2.4 Alternative-4

Do nothing and live with retransmissions in case of AMF not being ableto select an SMF.

2.3 Evaluation

Alternative-1 requires two NAS messages to transport a 5G SM messagewhile the existing procedure requires only 1 NAS message.Alternative-3 requires deployment of an SMF. The SMF does not need to befully functional—it only needs to be able to reject the 5GSM messagefrom the UE.Alternative-4 does not solve the problem.

4. Proposal

It is proposed to apply alternative-2.It is proposed to agree the following changes to 3GPP TR 24.890.8.5.1.1.2.1.1.4 Abnormal cases on the network sideThe following abnormal cases in AMF are identified:

-   -   a) if the AMF does not have a PDU session routing context for        the PDU session ID of the UL SM MESSAGE TRANSPORT message and        the UE, the request type IE of the UL SM MESSAGE TRANSPORT        message is set to “initial request”, and the SMF selection        fails, then the AMF shall create a 5GMM STATUS message. The AMF        shall set the 5GMM message container IE of the 5GMM STATUS        message to the UL SM MESSAGE TRANSPORT message. The AMF shall        set the cause IE of the 5GMM STATUS message to a cause        indicating cause of failure. The AMF shall send the 5GMM STATUS        message to the UE.    -   b) if the AMF does not have a PDU session routing context for        the PDU session ID of the UL SM MESSAGE TRANSPORT message and        the UE, the request type IE of the UL SM MESSAGE TRANSPORT        message is set to “existing PDU session”, and the user's        subscription context obtained from the UDM does not contain an        SMF ID corresponding to:        -   1) the DNN of the UL SM MESSAGE TRANSPORT message, if the            DNN is included in the NAS SM MESSAGE TRANSPORT message; or        -   2) the default DNN, if the DNN is not included in the UL SM            MESSAGE TRANSPORT message.        -   then the AMF shall create a 5GMM STATUS message. The AMF            shall set the 5GMM message container IE of the 5GMM STATUS            message to the UL SM MESSAGE TRANSPORT message. The AMF            shall set the cause IE of the 5GMM STATUS message to a cause            indicating cause of failure. The AMF shall send the 5GMM            STATUS message to the UE.    -   c) if the AMF does not have a PDU session routing context for        the PDU session ID of the UL SM MESSAGE TRANSPORT message and        the UE, and the request type IE of the UL SM MESSAGE TRANSPORT        message is not provided, then the AMF shall create a 5GMM STATUS        message. The AMF shall set the 5GMM message container IE of the        5GMM STATUS message to the UL SM MESSAGE TRANSPORT message. The        AMF shall set the cause IE of the 5GMM STATUS message to a cause        indicating cause of failure. The AMF shall send the 5GMM STATUS        message to the UE.    -   d) if the AMF has a PDU session routing context for the PDU        session ID of the UL SM MESSAGE TRANSPORT message and the UE,        the request type IE of the UL SM MESSAGE TRANSPORT message is        set to “initial request” and the AMF has not received a        reallocation requested indication, the AMF should forward the SM        message, the PDU session ID, the S-NSSAI (if received), the DNN        (if received) and the request type of the UL SM MESSAGE        TRANSPORT message towards the SMF ID of the PDU session routing        context.    -   e) if the AMF has a PDU session routing context for the PDU        session ID of the UL SM MESSAGE TRANSPORT message and the UE,        the PDU session routing context indicates that the PDU session        is an emergency PDU session, the request type IE of the UL SM        MESSAGE TRANSPORT message is set to “initial emergency request”,        the AMF should forward the SM message, the PDU session ID, the        S-NSSAI (if received), the DNN (if received) and the request        type of the UL SM MESSAGE TRANSPORT message towards the SMF ID        of the PDU session routing context.    -   f) if the AMF has a PDU session routing context for the PDU        session ID of the UL SM MESSAGE TRANSPORT message and the UE,        the request type IE of the UL SM MESSAGE TRANSPORT message is        set to “initial request”, the AMF has received a reallocation        requested indication from the SMF indicating that the SMF is to        be reallocated, and the PDU session routing context contains        reallocated SMF ID, the AMF should forward the SM message, the        PDU session ID, the S-NSSAI (if received), the DNN (if received)        and the request type of the UL SM MESSAGE TRANSPORT message        towards the reallocated SMF ID of the PDU session routing        context.        8.5.1.1.2.1.1.5 UE-initiated SM message transport initiation not        accepted by the network        Upon reception of 5GMM STATUS message with the 5GMM message        container IE containing an UL SM MESSAGE TRANSPORT message, the        UE passes a non-delivery indication along with the SM message of        the UL SM MESSAGE TRANSPORT message to the 5GSM procedures        specified in clause 9.        9.4.2.5 Abnormal cases in the UE        The following abnormal cases can be identified:    -   a) Tx expired    -   Editor's note: Further abnormal cases in the UE are FFS.    -   b) Upon receiving a non-delivery indication along with a PDU        SESSION ESTABLISHMENT REQUEST message with PTI IE set to the        allocated PTI value, the UE shall stop timer Tx, shall release        the allocated PTI value and shall consider that the PDU session        is not established.        9.4.4.5 Abnormal cases in the UE        The following abnormal cases can be identified:    -   a) Tk expired    -   Editor's note: Further abnormal cases are FFS.    -   b) Upon receiving a non-delivery indication along with a PDU        SESSION MODIFICATION REQUEST message with PTI IE set to the        allocated PTI value, the UE shall stop timer Tk, shall release        the allocated PTI value and shall consider that the PDU session        is not modified.        9.4.6.5 Abnormal cases in the UE        The following abnormal cases can be identified:    -   a) Tz expired    -   Editors' note: Further abnormal cases are FFS.    -   b) Upon receiving a non-delivery indication along with a PDU        SESSION RELEASE REQUEST message with PTI IE set to the allocated        PTI value, the UE shall stop timer Tz, shall release the        allocated PTI value and shall consider that the PDU session is        not released.

Abbreviations

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   1×RTT CDMA2000 1× Radio Transmission Technology-   3GPP 3rd Generation Partnership Project-   5G 5th Generation-   ABS Almost Blank Subframe-   ARQ Automatic Repeat Request-   AWGN Additive White Gaussian Noise-   BCCH Broadcast Control Channel-   BCH Broadcast Channel-   CA Carrier Aggregation-   CC Carrier Component-   CCCH SDU Common Control Channel SDU-   CDMA Code Division Multiplexing Access-   CGI Cell Global Identifier-   CIR Channel Impulse Response-   CP Cyclic Prefix-   CPICH Common Pilot Channel-   CPICH Ec/No CPICH Received energy per chip divided by the power    density in the band-   CQI Channel Quality information-   C-RNTI Cell RNTI-   CSI Channel State Information-   DCCH Dedicated Control Channel-   DL Downlink-   DM Demodulation-   DMRS Demodulation Reference Signal-   DRX Discontinuous Reception-   DTX Discontinuous Transmission-   DTCH Dedicated Traffic Channel-   DUT Device Under Test-   E-CID Enhanced Cell-ID (positioning method)-   E-SMLC Evolved-Serving Mobile Location Centre-   ECGIEvolved CGI-   eNB E-UTRAN NodeB-   ePDCCH enhanced Physical Downlink Control Channel-   E-SMLC evolved Serving Mobile Location Center-   E-UTRA Evolved UTRA-   E-UTRAN Evolved UTRAN-   FDD Frequency Division Duplex-   FFS For Further Study-   GERAN GSM EDGE Radio Access Network-   gNB Base station in NR-   GNSS Global Navigation Satellite System-   GSM Global System for Mobile communication-   HARQ Hybrid Automatic Repeat Request-   HO Handover-   HSPA High Speed Packet Access-   HRPD High Rate Packet Data-   LOS Line of Sight-   LPP LTE Positioning Protocol-   LTE Long-Term Evolution-   MAC Medium Access Control-   MBMS Multimedia Broadcast Multicast Services-   MBSFN Multimedia Broadcast multicast service Single Frequency    Network-   MBSFN ABS MBSFN Almost Blank Subframe-   MDT Minimization of Drive Tests-   MIB Master Information Block-   MME Mobility Management Entity-   MSC Mobile Switching Center-   NPDCCH Narrowband Physical Downlink Control Channel-   NR New Radio-   OCNG OFDMA Channel Noise Generator-   OFDM Orthogonal Frequency Division Multiplexing-   OFDMA Orthogonal Frequency Division Multiple Access-   OSS Operations Support System-   OTDOA Observed Time Difference of Arrival-   O&M Operation and Maintenance-   PBCH Physical Broadcast Channel-   P-CCPCH Primary Common Control Physical Channel-   PCell Primary Cell-   PCFICH Physical Control Format Indicator Channel-   PDCCH Physical Downlink Control Channel-   PDP Profile Delay Profile-   PDSCH Physical Downlink Shared Channel-   PGW Packet Gateway-   PHICH Physical Hybrid-ARQ Indicator Channel-   PLMN Public Land Mobile Network-   PMI Precoder Matrix Indicator-   PRACH Physical Random Access Channel-   PRS Positioning Reference Signal-   PSS Primary Synchronization Signal-   PUCCH Physical Uplink Control Channel-   PUSCH Physical Uplink Shared Channel-   RACH Random Access Channel-   QAM Quadrature Amplitude Modulation-   RAN Radio Access Network-   RAT Radio Access Technology-   RLM Radio Link Management-   RNC Radio Network Controller-   RNTI Radio Network Temporary Identifier-   RRC Radio Resource Control-   RRM Radio Resource Management-   RS Reference Signal-   RSCP Received Signal Code Power-   RSRP Reference Symbol Received Power OR-   Reference Signal Received Power-   RSRQ Reference Signal Received Quality OR-   Reference Symbol Received Quality-   RSSI Received Signal Strength Indicator-   RSTD Reference Signal Time Difference-   SCH Synchronization Channel-   SCell Secondary Cell-   SDU Service Data Unit-   SFN System Frame Number-   SGW Serving Gateway-   SI System Information-   SIB System Information Block-   SNR Signal to Noise Ratio-   SON Self Optimized Network-   SS Synchronization Signal-   SSS Secondary Synchronization Signal-   TDD Time Division Duplex-   TDOA Time Difference of Arrival-   TOA Time of Arrival-   TSS Tertiary Synchronization Signal-   TTI Transmission Time Interval-   UE User Equipment-   UL Uplink-   UMTS Universal Mobile Telecommunication System-   USIM Universal Subscriber Identity Module-   UTDOA Uplink Time Difference of Arrival-   UTRA Universal Terrestrial Radio Access-   UTRAN Universal Terrestrial Radio Access Network-   WCDMA Wide CDMA-   WLAN Wide Local Area Network

1. A method implemented in a wireless device, comprising: transmitting atransport message to a 3GPP Access and Mobility Function (AMF), whereinthe transport message comprises a session management message to beforwarded by the AMF to a 3GPP Session Management Function (SMF); andreceiving a status message transmitted by the AMF, wherein the statusmessage comprises at least a portion of the transport message and anindication of non-delivery of the session management message, whereinthe portion of the transport message comprises the session managementmessage, and the indication of non-delivery is an indication ofnon-delivery of the session management message by the AMF to the SMF. 2.The method of claim 1, wherein the transport message is a SM MessageTransport message; the session management message is a 5G sessionmanagement message; and the status message is a 5GMM Status message. 3.The method of claim 1, wherein the transport message further comprisesat least one of: a protocol data unit (PDU) session identifier, a datanetwork name, or a request type indication.
 4. The method of claim 1,wherein the session management message comprises a procedure transactionidentity indication identifying a session management transactionassociated with the session management message.
 5. The method of claim1, wherein the session management message is one of: (i) a sessionestablishment request message, (ii) a session modification requestmessage, or (iii) a session release request message, the method furthercomprising: as a result of receiving the indication of non-delivery,stopping a timer.
 6. The method of claim 5, the method furthercomprising: as a result of receiving the indication of non-delivery,determining that a session associated with the session managementmessage is: (i) not established, (ii) not modified, or (iii) notreleased.
 7. The method of claim 1, wherein the indication ofnon-delivery comprises a cause of failure to deliver the sessionmanagement message to a SMF.
 8. The method of any of claim 1, furthercomprising: providing user data; and forwarding the user data to a hostcomputer via the transmission to the base station.
 9. A wireless device,the wireless device comprising: a receiver; a transmitter; andprocessing circuitry coupled to the receiver and the transmitter,wherein the wireless device is configured to: transmit a transportmessage to a 3GPP Access and Mobility Function (AMF), wherein thetransport message comprises a session management message, to beforwarded by the AMF to a 3GPP Session Management Function (SMF); andreceive a status message transmitted by the AMF, wherein the statusmessage comprises at least a portion of the transport message and anindication of non-delivery of the session management message, whereinthe portion of the transport message comprises the session managementmessage, and the indication of non-delivery is an indication ofnon-delivery, by the AMF, to the 3GPP Session Management Function. 10.(canceled)
 11. A method performed by a 3GPP Access and MobilityManagement Function (AMF), comprising: receiving a transport messagetransmitted by a wireless device, wherein the transport messagecomprises a session management message; determining whether the sessionmanagement message can be forwarded to a 3GPP Session ManagementFunction (SMF); as a result of determining that the session managementmessage cannot be forwarded to a SMF, transmitting a status message tothe UE, the status message comprising at least a portion of thetransport message, wherein the portion of the transport messagecomprises the session management message and an indication ofnon-delivery of the session management message to a SMF.
 12. The methodof claim 11, wherein the determining whether the session managementmessage can be forwarded to a SMF is at least partly based on thetransport message.
 13. The method of claim 11, wherein the transportmessage is a SM Message Transport message; the session managementmessage is a 5G session management message; and the status message is a5GMM Status message.
 14. The method of claim 11, wherein the sessionmanagement message comprises a procedure transaction identity indicationidentifying a session management transaction associated with the sessionmanagement message.
 15. The method of claim 11, wherein the transportmessage further comprises at least one or more of: a protocol data unit(PDU) session identifier a data network name or a request typeindication.
 16. The method of claim 15, wherein the determining, atleast partly based on the transport message, whether the sessionmanagement message can be forwarded to a SMF further comprises:determining whether the AMF has a PDU session routing context for thePDU session identifier, wherein the request type indication indicatesthat the session management message is associated to an initial request;and as a result of determining that the AMF does not have a PDU sessionrouting context for the PDU session identifier, determining that a SMFcannot be selected for the session management message.
 17. The method ofclaim 15, wherein the determining, at least partly based on thetransport message, whether the session management message can beforwarded to a SMF further comprises: determining whether the AMF has aPDU session routing context for the PDU session identifier, wherein therequest type indication indicates that the session management message isassociated to an existing PDU session; obtaining subscription contextfor the wireless device from a unified data management (UDM), whereinthe subscription context comprises at least one or more SMF identifier(ID); and as a result of determining: (i) that the AMF does not have aPDU session routing context for the PDU session identifier and (ii) thatthe at least one or more SMF ID is not associated with the DNN,determining that a SMF cannot be selected for the session managementmessage.
 18. The method of claim 15, wherein the determining, at leastpartly based on the transport message, whether the session managementmessage can be forwarded to a SMF further comprises: determining whetherthe AMF has a PDU session routing context for the PDU sessionidentifier, wherein the request type indication indicates that thesession management message is associated to an existing PDU session, andthe DNN is not included in the transport message; obtaining subscriptioncontext for the wireless device from a unified data management, UDM,wherein the subscription context comprises at least one or more SMFidentifier, ID; and as a result of determining: (i) that the AMF doesnot have a PDU session routing context for the PDU session identifierand (ii) that the at least one or more SMF ID is not associated with adefault DNN, determining that a SMF cannot be selected for the sessionmanagement message.
 19. The method of claim 15, wherein the determining,at least partly based on the transport message, whether the sessionmanagement message can be forwarded to a SMF further comprises:determining whether the AMF has a PDU session routing context for thePDU session identifier, wherein the request type indication is notincluded in the transport message; and as a result of determining thatthe AMF does not have a PDU session routing context for the PDU sessionidentifier, determining that a SMF cannot be selected for the sessionmanagement message.
 20. The method of claim 11, wherein the indicationof non-delivery comprises a cause of failure to deliver the sessionmanagement message to a SMF.
 21. The method of claim 11, furthercomprising: obtaining user data; and forwarding the user data to a hostcomputer or a wireless device.
 22. A 3GPP Access and Mobility ManagementFunction (AMF) entity, entity configured to perform the method of claim11.
 23. The AMF entity of claim 22, wherein the determining whether thesession management message can be forwarded to a SMF is at least partlybased on the transport message.
 24. (canceled)